Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Mock chain ID and network version calls in simulation #3017

Merged
merged 2 commits into from
Jan 14, 2025

Conversation

FrederikBolding
Copy link
Member

Mock calls to eth_chainId and net_version in the simulation framework, so users don't have to mock them manually.

This should also prevent some flakiness in our tests.

@FrederikBolding FrederikBolding requested a review from a team as a code owner January 14, 2025 18:14
@FrederikBolding FrederikBolding force-pushed the fb/mock-chain-id-in-simulation branch from b11c90b to 5528ba9 Compare January 14, 2025 18:14
Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.76%. Comparing base (030ebee) to head (5528ba9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3017   +/-   ##
=======================================
  Coverage   94.75%   94.76%           
=======================================
  Files         497      499    +2     
  Lines       10896    10906   +10     
  Branches     1674     1674           
=======================================
+ Hits        10325    10335   +10     
  Misses        571      571           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Mrtenz Mrtenz merged commit 1ab6bc9 into main Jan 14, 2025
166 checks passed
@Mrtenz Mrtenz deleted the fb/mock-chain-id-in-simulation branch January 14, 2025 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants